Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0951

reference
611-tree-1
name
0951
tree-preservation-order

undefined

611-tpo-1
uprn
address-text
point
POINT (-1.027855 50.884285)
geometry
MULTIPOLYGON (((-1.027799 50.884279,-1.027801 50.884290,-1.027809 50.884300,-1.027821 50.884309,-1.027837 50.884314,-1.027855 50.884316,-1.027872 50.884314,-1.027888 50.884309,-1.027901 50.884301,-1.027909 50.884291,-1.027912 50.884280,-1.027910 50.884269,-1.027902 50.884259,-1.027889 50.884251,-1.027874 50.884246,-1.027856 50.884244,-1.027839 50.884245,-1.027823 50.884250,-1.027810 50.884258,-1.027802 50.884268,-1.027799 50.884279)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL